Metric Results

[ summary] [ packages] [ cycles] [ explanations]

The following document contains the results of a JDependmetric analysis. The various metrics are defined at the bottom of this document.

Summary

[ summary] [ packages] [ cycles] [ explanations]

Package	TC	AC	CC	AC	EC	A	I	D
ca.spaz.cron	6	0	6	8	19	0	70%	30%
ca.spaz.cron.config	3	2	1	2	2	0.67	50%	17%
ca.spaz.cron.database	12	4	8	8	5	0.33	38%	28%
ca.spaz.cron.datasource	8	5	3	5	8	0.62	62%	24%
ca.spaz.cron.datasource.sql	9	4	5	2	11	0.44	85%	29%
ca.spaz.cron.datasource.sql.USDAsr17	4	0	4	2	10	0	83%	17%
ca.spaz.cron.datasource.www	5	2	3	0	13	0.4	100%	40%
ca.spaz.cron.summary	18	3	15	1	17	0.17	94%	11%
ca.spaz.cron.targets	9	1	8	4	13	0.11	76%	12%
ca.spaz.cron.ui	46	0	46	1	27	0	96%	4%
ca.spaz.cron.user	11	3	8	5	17	0.27	77%	5%
ca.spaz.cron.user.impl	3	0	3	4	8	0	67%	33%
ca.spaz.gui	10	0	10	4	13	0	76%	24%
ca.spaz.sql	9	4	5	2	5	0.44	71%	16%
ca.spaz.task	7	2	5	4	5	0.29	56%	16%
ca.spaz.util	7	1	6	7	8	0.14	53%	32%
ca.spaz.wizard	5	1	4	1	7	0.2	88%	8%
com.aimedia.ui	7	3	4	4	8	0.43	67%	10%
com.nexes.wizard	6	0	6	0	9	0	100%	0%
se.datadosen.component	2	0	2	1	4	0	80%	20%

Packages

[ summary] [ packages] [ cycles] [ explanations]

Cycles

[ summary] [ packages] [ cycles] [ explanations]

Package	Cyclic Dependencies
ca.spaz.cron	ca.spaz.util ca.spaz.cron
ca.spaz.cron.database	ca.spaz.cron.datasource ca.spaz.cron.database
ca.spaz.cron.datasource	ca.spaz.cron.database ca.spaz.cron.datasource
ca.spaz.cron.datasource.sql	ca.spaz.cron ca.spaz.util ca.spaz.cron
ca.spaz.cron.datasource.sql.USDAsr17	ca.spaz.util ca.spaz.cron ca.spaz.util
ca.spaz.cron.datasource.www	ca.spaz.cron.datasource ca.spaz.cron.database ca.spaz.cron.datasource
ca.spaz.cron.summary	ca.spaz.cron.user ca.spaz.cron.database ca.spaz.cron.datasource ca.spaz.cron.database
ca.spaz.cron.targets	ca.spaz.cron.database ca.spaz.cron.datasource ca.spaz.cron.database
ca.spaz.cron.ui	ca.spaz.cron ca.spaz.util ca.spaz.cron
ca.spaz.cron.user	ca.spaz.cron.database ca.spaz.cron.datasource ca.spaz.cron.database
ca.spaz.cron.user.impl	ca.spaz.cron ca.spaz.util ca.spaz.cron
ca.spaz.util	ca.spaz.cron ca.spaz.util
ca.spaz.wizard	ca.spaz.util ca.spaz.cron ca.spaz.util

Explanations

[ summary] [ packages] [ cycles] [ explanations]

The following explanations are for quick reference and are lifted directly from the original JDepend documentation.

Term	Description
Number of Classes	The number of concrete and abstract classes (and interfaces) in the package is an indicator of the extensibility of the package.
Afferent Couplings	The number of other packages that depend upon classes within the package is an indicator of the package's responsibility.
Efferent Couplings	The number of other packages that the classes in the package depend upon is an indicator of the package's independence.
Abstractness	The ratio of the number of abstract classes (and interfaces) in the analyzed package to the total number of classes in the analyzed package. The range for this metric is 0 to 1, with A=0 indicating a completely concrete package and A=1 indicating a completely abstract package.
Instability	The ratio of efferent coupling (Ce) to total coupling (Ce / (Ce + Ca)). This metric is an indicator of the package's resilience to change. The range for this metric is 0 to 1, with I=0 indicating a completely stable package and I=1 indicating a completely instable package.
Distance	The perpendicular distance of a package from the idealized line A + I = 1. This metric is an indicator of the package's balance between abstractness and stability. A package squarely on the main sequence is optimally balanced with respect to its abstractness and stability. Ideal packages are either completely abstract and stable (x=0, y=1) or completely concrete and instable (x=1, y=0). The range for this metric is 0 to 1, with D=0 indicating a package that is coincident with the main sequence and D=1 indicating a package that is as far from the main sequence as possible.
Cycles	Packages participating in a package dependency cycle are in a deadly embrace with respect to reusability and their release cycle. Package dependency cycles can be easily identified by reviewing the textual reports of dependency cycles. Once these dependency cycles have been identified with JDepend, they can be broken by employing various object-oriented techniques.